-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend Privacy Policy with used Google scopes #954
Conversation
@Maxris @jorgeorpinel any idea why it does not run CircleCI for this branch from the top of your head? |
@@ -42,6 +42,13 @@ section of this User Guide. | |||
|
|||
## Scopes | |||
|
|||
userinfo.email scope (view your email address), userinfo.profile scope (see your |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's use userinfo.email
(inline code) blocks for scope names to make a bit more readable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shcheklein have updated markup and have added mention about drive.appdata
scope as well.
Not sure why CicrcleCI won't start (how it might be related to my GitHub account).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Maxris don't worry about this for now. Have asked their support to check what the issue could be.
your personal info, including any personal info you've made publicly available), | ||
and `openid` scope (authenticate using OpenID Connect) are required to be used | ||
by Google Auth. DVC authorizes users via | ||
[Google's server](https://accounts.google.com/o/oauth2/auth) and doesn't access |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! This link doesn't work like this. Should we just display it instead like `https://accounts.google.com/o/oauth2/auth`
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jorgeorpinel , the idea here was to mention explicitly that server belongs to Google and link was added just as a prove. Also link might change with time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also not sure why it doesn't work? I can click at "Google's server" text and the URL is opened in new tab ( error in new tab is displayed, but it is fine )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think @jorgeorpinel refers to the fact that it returns 404 and looks like broken bc of that. Also trigger our CI scripts that detect broken/dead links. I've added it to the exclusion list for now. Still, not clear if it makes sense to keep it this way, even though I understand the intention.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, we need it in the link exclusion list anyway, but it's best to display the link in the markdown like a `quote`
instead of a clickable link, I think.
And yes, I meant it's not a link to any useful website. It doesn't work like that = it's not meant to be navigated, just the base URL to begin a OAuth authentication (but needs a special token in the URL query)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jorgeorpinel got it, thanks, should I propose the changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jorgeorpinel let's fix it as part of the regular updates flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to keep kicking a dead horse but I have another follow up question to this PR guys: Will the current guide in https://dvc.org/doc/user-guide/setup-google-drive-remote be completely rewritten soon? Since we're using a default DVC Application on GCP it seems to me the guide will be much simpler, but maybe this isn't completely done yet (Google APIs verification process). |
@jorgeorpinel it'll be augmented most likely, not rewritten. We still recommend using your own app/project. |
No description provided.